Configuring JMS and ActiveMQ for Reliable Messaging |
|
Before you begin this task
Ensure the following:
- Load the Process Platform JMSTransport package.
- Install ActiveMQ.
- Install Atomikos.
- After installing, set the system CLASSPATH accordingly depending upon the operating system.
- For Windows: Add the following JARs to the system variable CLASSPATH.
- For Linux: Extend the CLASSPATH with the JAR files at the location
<Process Platform Home Directory>\bin\wcpenv.sh
.- Process Platform:
<Process Platform Home Directory>/ext/jms.jar
<Process Platform Home Directory>/components/jmstransport/jmstransport.jar - ActiveMQ:
<ActiveMQ Home Directory>/activemq-all-5.6.0.jar
<ActiveMQ Home Directory>/lib/slf4j-api-1.6.4.jar - Atomikos and additional:
<AtomikosHome>/atomikos-util.jar
<AtomikosHome>/transactions.jar
<AtomikosHome>/transactions-api.jar
<AtomikosHome>/transactions-jta.jar
<AtomikosHome>/slf4j-nop.jar*}}
- Process Platform:
- Include the
slf4j-nop.jar
in the service container classpath. You can download it from http://www.slf4j.org/download.html. - For Tomee: Add all the above JARs to the Web Gateway CLASSPATH.
- Set the global configuration.
- Go to CUSP > My Applications, click ( System Resource Manager). The System Resource Manager window appears displaying the list of all the available service containers.
- Right-click a service container and select Manage Connection Points. The Connection Points dialog box appears listing the existing connection points.
- Click . The Connection Point dialog box appears.
- In the Connection Point dialog box, do the following:
Specify a Name for the connection end point. For example, BPMconnection.
Select the Type as JMS.
Select the Use distributed transaction manager check box.
Provide a Queue Name, for example, system.BPM.
- Click Save.
The connection point is created.
Note: No additional or manual steps are needed within ActiveMQ. When a JMS endpoint is created, queues are automatically created within ActiveMQ. Click here for a sample screenshot.